-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
testing: Explicitly pass -Werror
to tests needing it
#13481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bluetech
reviewed
Jun 3, 2025
mgorny
added a commit
to mgorny/pytest
that referenced
this pull request
Jun 3, 2025
Explicitly pass `-Werror` to `runpytester()` in the few additional tests needing it, in order to fix test failures when the test suite is run with `-Wdefault` or a similar override. Fixes pytest-dev#13480
bluetech
approved these changes
Jun 18, 2025
The unraisableexception tests were handled in another PR, so this is ready to go. I tweaked the changelog a bit. |
Thanks! |
Backport to 8.4.x: 💚 backport PR created✅ Backport PR branch: Backported as #13538 🤖 @patchback |
patchback bot
pushed a commit
that referenced
this pull request
Jun 18, 2025
testing: Explicitly pass `-Werror` to tests needing it (cherry picked from commit 667398f)
Merged
6 tasks
bluetech
added a commit
that referenced
this pull request
Jun 18, 2025
…67398f53b7ca9a19a540054b03d505b84379114/pr-13481 [PR #13481/667398f5 backport][8.4.x] testing: Explicitly pass `-Werror` to tests needing it
nicoddemus
reviewed
Jun 18, 2025
nicoddemus
added a commit
to nicoddemus/pytest
that referenced
this pull request
Jun 22, 2025
Since this is related only to internal testing and does not affect end-users, it is more appropriate to announce it in the "Contributor" section of the changelog. Follow up to pytest-dev#13481.
nicoddemus
added a commit
that referenced
this pull request
Jun 24, 2025
Since this is related only to internal testing and does not affect end-users, it is more appropriate to announce it in the "Contributor" section of the changelog. Follow up to #13481.
nicoddemus
added a commit
that referenced
this pull request
Jun 24, 2025
Since this is related only to internal testing and does not affect end-users, it is more appropriate to announce it in the "Contributor" section of the changelog. Follow up to #13481. (cherry picked from commit cc580b5) Co-authored-by: Bruno Oliveira <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport 8.4.x
apply to PRs at any point; backports the changes to the 8.4.x branch
bot:chronographer:provided
(automation) changelog entry is part of PR
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explicitly pass
-Werror
torunpytester()
in the few additional tests needing it, in order to fix test failures when the test suite is run with-Wdefault
or a similar override.Fixes #13480
If this change fixes an issue, please:
closes #XYZW
to the PR description and/or commits (whereXYZW
is the issue number). See the github docs for more information.Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:
Create a new changelog file in the
changelog
folder, with a name like<ISSUE NUMBER>.<TYPE>.rst
. See changelog/README.rst for details.Write sentences in the past or present tense, examples:
Also make sure to end the sentence with a
.
.Add yourself to
AUTHORS
in alphabetical order.